ci: merge the release-please PR automatically - #25
Merged
Conversation
main has no required checks and repo-level auto-merge is disabled, so gh pr merge --auto is unavailable here. Merge the release PR directly when release-please opens it, so a code merge to main flows straight through to a tag and publish without a second manual merge.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Problem
Publishing takes two manual merges. Merging the
stainless/releasecode PR runsrelease-please.yml, which only opens a release PR (version bump + changelog). Nothing publishes until that second PR is also merged.Fix
Merge the release PR automatically the moment release-please opens/updates it, so a code merge to
mainflows straight through to a tag + publish with no second manual merge.gh pr merge --autois not usable here: the repo has "Allow auto-merge" disabled andmainhas no required checks, so auto-merge errors with "clean status." The step merges directly with--squash(the only enabled merge method) instead.Behavior change
Every code merge to
mainnow publishes immediately (continuous release). Mirrors linq-team/linq-node#72.